Gateway User Information for PBX Extensions and "Global" Numbers

The GW User Information table contains information of Gateway users, which can be used for the following Gateway-related features:

■

Mapping (Manipulating) PBX Extension Numbers with Global Phone Numbers: maps PBX extension number, connected to the device, with any "global" phone number (alphanumerical) for the IP side. In this context, the "global" phone number serves as a routing identifier for calls in the "IP world" and the PBX extension uses this mapping to emulate the behavior of an IP phone. This feature is especially useful in scenarios where unique or non-consecutive number translation per PBX is needed. This number manipulation feature supports the following call directions:

●

IP-to-Tel Calls: Maps the called "global" number (in the Request-URI user part) to the PBX extension number. For example, if the device receives an IP call destined for "global" number 638002, it changes this called number to the PBX extension number 402, and then sends the call to the PBX extension on the Tel side.

If you have configured regular IP-to-Tel manipulation rules (see Configuring Source-Destination Number Manipulation Rules), the device applies these rules before applying the mapping rules of the GW User Information table.

●

Tel-to-IP Calls: Maps the calling (source) PBX extension to the "global" number. For example, if the device receives a Tel call from PBX extension 402, it changes this calling number to 638002, and then sends call to the IP side with this calling number. In addition to the "global" phone number, the display name (caller ID) configured for the PBX user in the GW User Information table is used in the SIP From header.

If you have configured regular Tel-to-IP manipulation rules (see Configuring Source-Destination Number Manipulation Rules), the device applies these rules before applying the mapping rules of the GW User Information table.

■

Registering Users: The device can register each PBX user configured in the GW User Information table. For each user, the device sends a SIP REGISTER to an external IP-based Registrar server, using the "global" number in the From/To headers. If authentication is necessary for registration, the device sends the user's username and password, configured in the GW User Information table, in the SIP MD5 Authorization header.

You can configure up to 500 mapping rules in the GW User Information table. These rules can be configured using any of the following methods:

■

Web interface - see Configuring Gateway User Information Table through Web Interface

■

CLI - see Configuring Gateway User Information Table through CLI

■

Loadable User Information file - see Configuring Gateway User Information Table from a Loadable File

●

This section is applicable only to the Gateway application.

●

To enable user registration, configure the following parameters:

✔

'Enable Registration': Enable or [IsRegisterNeeded] set to 1

✔

'Registration Mode': Per Endpoint or [AuthenticationMode] set to 0

●

For FXS ports, when the device needs to send a new SIP request with the Authorization header (e.g., after receiving a SIP 401 response), it uses the username and password configured in the Authentication table (see Configuring Authentication). To use the username and password that are configured in the GW User Information table, configure the 'Password' parameter to any value other than its default value.